Triple
T3637712
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Control Yuan |
E77111
|
entity |
| Predicate | hasNumberOfBranchesInSystem |
P1989
|
FINISHED |
| Object | five |
—
|
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: five | Statement: [Control Yuan, hasNumberOfBranchesInSystem, five]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNumberOfBranchesInSystem Context triple: [Control Yuan, hasNumberOfBranchesInSystem, five]
-
A.
branchCount
chosen
Indicates the number of branches associated with a given entity or structure.
-
B.
hasTwoBranches
Indicates that the related entity is divided into or composed of exactly two distinct branches.
-
C.
hasMajorBranch
Indicates that one entity possesses or includes another entity as a primary or principal subdivision or branch.
-
D.
hasNumberOfBridges
Indicates the quantitative relationship specifying how many bridges are associated with a given entity.
-
E.
hasSummaryBranches
Indicates that an entity includes or is associated with summarized versions or high-level branches derived from more detailed components or structures.
- 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_69ad85dd0be48190b738990cb20c4731 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc328e5e481909d26318c743bc84a |
completed | March 8, 2026, 6:42 p.m. |
| PD | Predicate disambiguation | batch_69adb842be7c8190b7dfdb7c906f294c |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:24 p.m.