Triple
T8498340
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | podrace on Tatooine |
E201152
|
entity |
| Predicate | audienceWithinUniverse |
P47705
|
FINISHED |
| Object | large in-person crowd |
—
|
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: large in-person crowd | Statement: [podrace on Tatooine, audienceWithinUniverse, large in-person crowd]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: audienceWithinUniverse Context triple: [podrace on Tatooine, audienceWithinUniverse, large in-person crowd]
-
A.
inUniverseSpeaker
Indicates that the subject is a speaker or narrator who exists within the fictional universe or narrative world being described.
-
B.
inUniverse
chosen
Indicates that one entity exists, occurs, or is set within the fictional or conceptual universe defined by another entity.
-
C.
audienceScale
Indicates the relative size or reach of the audience associated with an entity, event, or communication.
-
D.
relatesToAudience
Indicates a general relationship or relevance between something and a particular audience or group of recipients.
-
E.
audienceComposition
Indicates the makeup or distribution of different groups or segments within an audience in relation to something.
- 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_69ca831ee390819095fae73400bbfafc |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe583aebc819090345684bfa1fca2 |
completed | March 31, 2026, 3:17 p.m. |
| PD | Predicate disambiguation | batch_69cbd10a4b0881909e254117780dc823 |
completed | March 31, 2026, 1:50 p.m. |
Created at: March 30, 2026, 6:14 p.m.