Triple
T2863306
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fandom |
E63376
|
entity |
| Predicate | hasSubdomainStructure |
P28415
|
FINISHED |
| Object | individual wikis per topic |
—
|
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: individual wikis per topic | Statement: [Fandom, hasSubdomainStructure, individual wikis per topic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSubdomainStructure Context triple: [Fandom, hasSubdomainStructure, individual wikis per topic]
-
A.
hasSubdomain
chosen
Indicates that one domain is a subordinate or nested part of another domain within a hierarchical naming structure.
-
B.
isSubnetworkOf
Indicates that one network is a contained, subordinate, or component part of another, larger network.
-
C.
hasSubsidiaryLabel
Indicates that one entity is identified as a subsidiary or subordinate organization of another entity.
-
D.
hasSubOrganizationType
Indicates that an organization is associated with or classified under a specific type or category of sub-organization.
-
E.
hasStructureAbove
Indicates that one entity has another entity positioned vertically higher or located on top of it within a structural or spatial arrangement.
- 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_69ab4c41e8c08190a9e8f5249cc12610 |
completed | March 6, 2026, 9:50 p.m. |
| NER | Named-entity recognition | batch_69abdfb6e6988190b832ee05d8420633 |
completed | March 7, 2026, 8:20 a.m. |
| PD | Predicate disambiguation | batch_69abdd123ec48190af50a1859aea50b7 |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 10:02 p.m.