Triple
T17912084
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brainiac |
E447838
|
entity |
| Predicate | signatureActivity |
P104649
|
FINISHED |
| Object | shrinking cities |
—
|
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: shrinking cities | Statement: [Brainiac, signatureActivity, shrinking cities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: signatureActivity Context triple: [Brainiac, signatureActivity, shrinking cities]
-
A.
signatureEventOf
Indicates that a given event represents or records the signing (or creation) of the associated entity, such as a document, agreement, or artifact.
-
B.
signatureEvent
Indicates an event in which an entity formally signs or authorizes something, such as a document, agreement, or record.
-
C.
signature
Indicates that one entity has provided an official or personal signed endorsement, authorization, or acknowledgment on or for another entity.
-
D.
signatureAbilityType
Indicates the specific category or kind of distinctive or defining ability associated with an entity.
-
E.
signatureContribution
chosen
Indicates that an entity has made a defining or hallmark contribution that is strongly characteristic of their work, style, or influence.
- 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_69d8b9f6d394819082a6d69fd1e23d2f |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e49ea0ea008190b54a999e0704fb67 |
completed | April 19, 2026, 9:21 a.m. |
| PD | Predicate disambiguation | batch_69e3d8ec2f6881909d7f54b878cbed37 |
completed | April 18, 2026, 7:18 p.m. |
Created at: April 10, 2026, 10:19 a.m.