Triple
T24161928
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rainha da Borborema |
E598862
|
entity |
| Predicate | refereSeA |
P63266
|
FINISHED |
| Object | Campina Grande |
—
|
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: Campina Grande | Statement: [Rainha da Borborema, refereSeA, Campina Grande]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: refereSeA Context triple: [Rainha da Borborema, refereSeA, Campina Grande]
-
A.
referredTo
Indicates that one entity has mentioned, directed attention to, or cited another entity as a point of reference.
-
B.
alsoRefersTo
chosen
Indicates that one term, label, or identifier is used as an alternative designation for the same entity or concept as another.
-
C.
referenceSectionFor
Indicates a relationship where one resource serves as the reference section or reference material specifically associated with another resource.
-
D.
canRefer
Indicates that one entity has the ability or permission to mention, point to, or direct attention to another entity.
-
E.
notablyRefersTo
Indicates that one entity makes a particularly significant or noteworthy reference to another entity, beyond a routine or incidental mention.
- 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_69e288cb0a3081909ef221744f274384 |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1e0e9cd6c81908c33242f19fcc034 |
completed | April 29, 2026, 10:43 a.m. |
| PD | Predicate disambiguation | batch_69f176585f3481909beb907de252cd98 |
completed | April 29, 2026, 3:09 a.m. |
Created at: April 17, 2026, 11:32 p.m.