Triple
T7888194
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Caroline Gomes |
E183156
|
entity |
| Predicate | notabilityScope |
P79581
|
FINISHED |
| Object | international |
—
|
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: international | Statement: [Caroline Gomes, notabilityScope, international]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notabilityScope Context triple: [Caroline Gomes, notabilityScope, international]
-
A.
notabilityStatus
Indicates whether and how an entity is recognized as notable or significant within a given context or system.
-
B.
notabilityReason
Indicates the specific cause, basis, or context for which an entity is considered notable or significant.
-
C.
organNotability
Indicates that an organ is notable or significant in some specific context or for a particular purpose.
-
D.
notedIn
Indicates that information about one entity is mentioned, recorded, or referenced within another entity, such as a document, record, or source.
-
E.
notableDrive
Indicates that an entity is particularly recognized or distinguished for its driving performance, experience, or characteristics.
- F. None of above. chosen
Provenance (4 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_69ca828af6e48190a06ee7010d8f0e64 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb39ea8d1c81908ef99569e0cf00b7 |
completed | March 31, 2026, 3:05 a.m. |
| PD | Predicate disambiguation | batch_69cae92b0cd881908e715a10d3252e83 |
completed | March 30, 2026, 9:20 p.m. |
| PDg | Predicate description generation | batch_69caf786ec748190b6347b0c94335550 |
completed | March 30, 2026, 10:21 p.m. |
Created at: March 30, 2026, 4:59 p.m.