Triple
T24076224
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treaty of Tripoli (English version, 1797) |
E596367
|
entity |
| Predicate | locationRatified |
P154760
|
FINISHED |
| Object | Philadelphia |
E171
|
NE 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: Philadelphia | Statement: [Treaty of Tripoli (English version, 1797), locationRatified, Philadelphia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locationRatified Context triple: [Treaty of Tripoli (English version, 1797), locationRatified, Philadelphia]
-
A.
locationScrapped
Indicates that the location associated with an entity has been removed, discarded, or is no longer considered valid or in use.
-
B.
propertyLocation
Indicates the geographical place or address where a property is situated or found.
-
C.
locationFormed
Indicates the place or geographic area where an entity (such as an organization, group, or structure) was originally established or came into existence.
-
D.
locationPresented
Indicates that a specific location is presented or shown to an entity (such as a user or system) within a given context.
-
E.
locationWhenGiven
Indicates the place where an entity is located at the time it is given or transferred to another entity.
- F. None of above. chosen
Provenance (5 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_69e288c3999c8190809b282a04813dec |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1db1dd874819087120b06b90be485 |
completed | April 29, 2026, 10:19 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a0fc9981d5881909d9602e515fdb957 |
completed | May 22, 2026, 3:12 a.m. |
| PD | Predicate disambiguation | batch_69f1764b1d4c8190b12590c6339c31c1 |
completed | April 29, 2026, 3:08 a.m. |
| PDg | Predicate description generation | batch_69f1785afe3c81909be28986ffe944bf |
completed | April 29, 2026, 3:17 a.m. |
Created at: April 17, 2026, 10:42 p.m.