Triple
T5417962
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Karapan sapi |
E121177
|
entity |
| Predicate | hasTeamStructure |
P63540
|
FINISHED |
| Object | pair of yoked bulls |
—
|
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: pair of yoked bulls | Statement: [Karapan sapi, hasTeamStructure, pair of yoked bulls]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTeamStructure Context triple: [Karapan sapi, hasTeamStructure, pair of yoked bulls]
-
A.
hasOrganizationalStructure
Indicates that an entity possesses a defined internal arrangement of roles, responsibilities, and relationships that determine how it is organized and operates.
-
B.
hasSubteam
Indicates that one team is a subordinate or component team within another, larger team.
-
C.
hasIndependentTeams
Indicates that an entity possesses or is associated with teams that operate autonomously from other teams or central control.
-
D.
hasCurrentTeam
Indicates that an entity is presently a member of or affiliated with a specific team.
-
E.
hasNumberOfTeams
Indicates the quantity of teams associated with or contained by a given 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_69bd463a41cc8190b32ff5af2b96ca93 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd87e620f081909eb9a5e1f284e5a2 |
completed | March 20, 2026, 5:46 p.m. |
| PD | Predicate disambiguation | batch_69bd8469f5e48190bbe5c8bdfe8925ea |
completed | March 20, 2026, 5:31 p.m. |
| PDg | Predicate description generation | batch_69bd8741e8588190863fd5cfb559136d |
completed | March 20, 2026, 5:43 p.m. |
Created at: March 20, 2026, 2:05 p.m.