Triple
T2545864
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prufrock tunnel boring machine |
E57899
|
entity |
| Predicate | usedForProjectType |
P4243
|
FINISHED |
| Object | Loop transportation tunnels |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Loop transportation tunnels | Statement: [Prufrock tunnel boring machine, usedForProjectType, Loop transportation tunnels]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedForProjectType Context triple: [Prufrock tunnel boring machine, usedForProjectType, Loop transportation tunnels]
-
A.
supportsProjectType
chosen
Indicates that one entity is capable of handling, accommodating, or being compatible with a specified type of project.
-
B.
hasProjectType
Indicates that an entity is associated with, or classified under, a specific type or category of project.
-
C.
usedInProject
Indicates that something (such as a resource, tool, or component) is employed or utilized within a particular project.
-
D.
usedInType
Indicates that something serves as a component, element, or example within a particular type or category.
-
E.
usesToolType
Indicates that an entity performs an action or fulfills a role by employing a specific type or category of tool.
- F. None of above.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69ab4a5212d88190b989ce129f2ad87f |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abd2c285288190b41fc0188879623a |
completed | March 7, 2026, 7:24 a.m. |
| PD | Predicate disambiguation | batch_69abd0c63964819092d5f578195ae8dd |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:47 p.m.