Triple
T32011050
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | We’re Here |
E817401
|
entity |
| Predicate | timePeriodOfFictionalOperation |
P60994
|
FINISHED |
| Object | late 19th century |
—
|
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: late 19th century | Statement: [We’re Here, timePeriodOfFictionalOperation, late 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timePeriodOfFictionalOperation Context triple: [We’re Here, timePeriodOfFictionalOperation, late 19th century]
-
A.
timeOfMission
Indicates the specific time or period during which a mission takes place or is scheduled.
-
B.
fictionalTime
chosen
Indicates that the associated time or temporal reference exists only within a fictional or imagined context, rather than in real-world chronology.
-
C.
eraOfOperation
Indicates the time period or span of years during which an entity was active or in operation.
-
D.
durationDepicted
Indicates that a representation (such as a media item or depiction) specifies or conveys the length of time over which an event, process, or state occurs.
-
E.
missionDurationType
Indicates the classification of a mission’s length or time span (e.g., short-term, long-term, extended).
- 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_69f348f9e5d081908cc3f57c4942af52 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f760a35b988190904e6267553ad2fe |
completed | May 3, 2026, 2:50 p.m. |
| PD | Predicate disambiguation | batch_69f75eb3d6f081908c933474eb359e3d |
completed | May 3, 2026, 2:41 p.m. |
Created at: May 1, 2026, 12:15 a.m.