Triple
T6632419
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Campina Grande |
E149957
|
entity |
| Predicate | hasFoundedAs |
P364
|
FINISHED |
| Object | settlement in the 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: settlement in the 17th century | Statement: [Campina Grande, hasFoundedAs, settlement in the 17th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFoundedAs Context triple: [Campina Grande, hasFoundedAs, settlement in the 17th century]
-
A.
foundedAs
chosen
Indicates the original name or form under which an organization, institution, or entity was first established.
-
B.
foundedWith
Indicates that an entity was established or created together with another entity, typically as co-founders or jointly initiated partners.
-
C.
foundedFor
Indicates that an entity was established or created specifically to serve, support, or benefit another entity or purpose.
-
D.
foundedFrom
Indicates that an entity was established or originated starting from a particular source, place, or prior entity.
-
E.
foundedBefore
Indicates that one entity was established or created at an earlier time than the other 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_69c687ee50048190aa151765bef16193 |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6c308a08881908501c862b3029321 |
completed | March 27, 2026, 5:48 p.m. |
| PD | Predicate disambiguation | batch_69c6ad024860819084b9b535b136ede6 |
completed | March 27, 2026, 4:14 p.m. |
Created at: March 27, 2026, 1:59 p.m.