Triple
T6667399
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | La Máquina |
E151637
|
entity |
| Predicate | associatedWithFanbaseSize |
P67894
|
FINISHED |
| Object | large national following |
—
|
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 national following | Statement: [La Máquina, associatedWithFanbaseSize, large national following]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithFanbaseSize Context triple: [La Máquina, associatedWithFanbaseSize, large national following]
-
A.
fanBaseSize
chosen
Indicates the size or magnitude of the group of fans or supporters associated with an entity.
-
B.
hasFanBaseFrom
Indicates that an entity has a significant group of supporters or followers originating from a specified place, group, or source.
-
C.
fanBaseRelationship
Indicates a relationship in which one party is a fan or supporter of another, typically involving admiration, following, or dedicated interest.
-
D.
fanBaseScope
Indicates the extent or range of people who are considered fans or followers of an entity.
-
E.
hasFanBaseTension
Indicates a relationship where there is conflict, rivalry, or strained relations between the fan bases of the related entities.
- 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_69c687f71fc081909dbd45d6377f6045 |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6ce738fe88190a5557900efeec7ec |
completed | March 27, 2026, 6:37 p.m. |
| PD | Predicate disambiguation | batch_69c6ad09974c81908784300ae218961f |
completed | March 27, 2026, 4:15 p.m. |
Created at: March 27, 2026, 2:02 p.m.