Triple
T35567421
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ladakh Autonomous Hill Development Council, Leh |
E1027814
|
entity |
| Predicate | hasNumberOfNominatedCouncillors |
P198223
|
FINISHED |
| Object | 4 |
—
|
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: 4 | Statement: [Ladakh Autonomous Hill Development Council, Leh, hasNumberOfNominatedCouncillors, 4]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNumberOfNominatedCouncillors Context triple: [Ladakh Autonomous Hill Development Council, Leh, hasNumberOfNominatedCouncillors, 4]
-
A.
hasNumberOfCouncillors
Indicates the relationship that specifies how many councillors are associated with a given entity.
-
B.
hasCouncillors
Indicates that an entity is associated with one or more councillors who serve or represent it in an official capacity.
-
C.
hasNumberOfNominatedMembers
chosen
Indicates that an entity is associated with a specific count of members who have been formally nominated.
-
D.
hasNominatedMembers
Indicates that an entity has selected and put forward specific individuals to serve as members of another body, group, or role.
-
E.
hasNumberOfDeputies
Indicates the specific count of deputies associated with or assigned to an entity.
- 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_69f76e020fd8819081cb080e7e203083 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fefb15220081908da36aac386fa582 |
completed | May 9, 2026, 9:15 a.m. |
| PD | Predicate disambiguation | batch_69fefa8e8ad48190a723fed81e9d64d0 |
completed | May 9, 2026, 9:12 a.m. |
Created at: May 3, 2026, 4:04 p.m.