Triple
T6113435
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Franklin Square |
E136299
|
entity |
| Predicate | laidOutIn |
P56790
|
FINISHED |
| Object | late 17th 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 17th century | Statement: [Franklin Square, laidOutIn, late 17th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laidOutIn Context triple: [Franklin Square, laidOutIn, late 17th century]
-
A.
wasLaidOutIn
chosen
Indicates that something was arranged, designed, or planned within a particular time period or event.
-
B.
laidDownAs
Indicates that one entity has been formally established, stipulated, or prescribed as a rule, principle, or condition for another.
-
C.
laidDown
Indicates that an entity places or sets another entity down into a resting or horizontal position.
-
D.
laidDownBy
Indicates that something was established, created, or set as a rule, principle, or foundation by a particular agent.
-
E.
hasLayOrder
Indicates that one entity has issued, received, or is subject to a formal lay order associated with another entity.
- 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_69c0089ea6f88190b349be53e04b4f5f |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c05bbf2ee4819097af2cce9248bf4e |
completed | March 22, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69c049f80e2081909b7d84a104cda68d |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:14 p.m.