Triple
T36003977
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Macro-Gulf (proposed) |
E1041211
|
entity |
| Predicate | hasPeerReception |
P196474
|
FINISHED |
| Object | not part of standard language family classifications |
—
|
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: not part of standard language family classifications | Statement: [Macro-Gulf (proposed), hasPeerReception, not part of standard language family classifications]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPeerReception Context triple: [Macro-Gulf (proposed), hasPeerReception, not part of standard language family classifications]
-
A.
hasReception
Indicates that an entity hosts, includes, or is associated with a reception event (such as a formal gathering or welcoming function).
-
B.
hasReceiver
Indicates that an entity serves as the recipient or target of something provided, sent, or directed by another entity.
-
C.
hasAmbiguousReception
Indicates that the reception or response to something is mixed, unclear, or open to multiple interpretations.
-
D.
hasReviewReception
Indicates that an entity has received a critical or evaluative review describing how it was received or perceived.
-
E.
receivedTransmissionOf
Indicates that one entity has obtained or been sent a transmission (such as a message, signal, or data) originating from another entity.
- 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_69f76e2a02208190aedd1f9025a8b300 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fe38be079c8190a240191ac0e73e3a |
completed | May 8, 2026, 7:25 p.m. |
| PD | Predicate disambiguation | batch_69fe350344508190930de2218156ca02 |
completed | May 8, 2026, 7:09 p.m. |
| PDg | Predicate description generation | batch_69fe38bc3e9c8190838430b22b82503f |
completed | May 8, 2026, 7:25 p.m. |
Created at: May 3, 2026, 4:07 p.m.