Triple
T37227029
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | T.C. |
E923031
|
entity |
| Predicate | basedInSettingType |
P119780
|
FINISHED |
| Object | alley |
—
|
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: alley | Statement: [T.C., basedInSettingType, alley]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: basedInSettingType Context triple: [T.C., basedInSettingType, alley]
-
A.
basedInSetting
chosen
Indicates that an entity is situated, located, or primarily operates within a particular setting or environment.
-
B.
basedOnSetting
Indicates that one entity is derived from, influenced by, or constructed using the setting or contextual environment defined by another entity.
-
C.
basedInSeriesSetting
Indicates that something (such as a work, event, or element) is situated within or occurs in the primary setting established by a particular series.
-
D.
basedInUntil
Indicates that an entity was based or located in a particular place up to a specified end time or date, after which this association ceased.
-
E.
basedInPartIn
Indicates that an entity is located or operates partially within a specified place or region, but not entirely.
- 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_69f76ea7f0008190b31b8e30f3d05a71 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ff6074bcd4819090b72cd6209ff206 |
completed | May 9, 2026, 4:27 p.m. |
| PD | Predicate disambiguation | batch_69ff600aba888190812a6e7eca0283b8 |
completed | May 9, 2026, 4:25 p.m. |
Created at: May 3, 2026, 4:15 p.m.