Triple
T30949754
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Harrisburg, Texas |
E788502
|
entity |
| Predicate | wasFocalPointDuring |
P130867
|
FINISHED |
| Object | Runaway Scrape |
—
|
NE NERFINISHED |
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: Runaway Scrape | Statement: [Harrisburg, Texas, wasFocalPointDuring, Runaway Scrape]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasFocalPointDuring Context triple: [Harrisburg, Texas, wasFocalPointDuring, Runaway Scrape]
-
A.
wasTargetDuring
Indicates that an entity served as the target of another entity or action during a specified time period or event.
-
B.
wasIn
Indicates that an entity existed, occurred, or was located within a particular place or context during a specified time or situation.
-
C.
hasFocalPoint
chosen
Indicates that something possesses a central point of focus or primary area of attention within its structure, composition, or activity.
-
D.
hadFocus
Indicates that an entity previously possessed or maintained primary attention, emphasis, or priority within a given context or interaction.
-
E.
wereInternedBy
Indicates that an entity was forcibly confined, detained, or held in an internment facility by another entity (typically an authority or government).
- 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_69f224c180f88190ad177372ee02b7e2 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6953bafb88190a860e9c68a3dd4b2 |
completed | May 3, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69f690ef92308190903a54fc74233269 |
completed | May 3, 2026, 12:03 a.m. |
Created at: April 29, 2026, 8:53 p.m.