Triple
T6514401
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | S47 |
E148216
|
entity |
| Predicate | networkMapSymbol |
P19295
|
FINISHED |
| Object | S47 |
—
|
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: S47 | Statement: [S47, networkMapSymbol, S47]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: networkMapSymbol Context triple: [S47, networkMapSymbol, S47]
-
A.
networkMapName
Indicates the designated name or label assigned to a particular network map within a system or context.
-
B.
mapSymbol
chosen
Indicates a correspondence where one symbol is used to represent, stand for, or denote another element within a mapping or representation system.
-
C.
networkModel
Indicates a relationship where an entity is represented or organized according to a specific network-based structure or framework.
-
D.
network
Indicates that one entity is connected to or interacts with another through a system of relationships, communication, or information exchange.
-
E.
originalNetworkDepicted
Indicates that one entity visually represents or portrays the original network associated with another 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_69c687e68e748190baceb9298f32d3ed |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6ac0bea808190aebc2905fb53eeba |
completed | March 27, 2026, 4:10 p.m. |
| PD | Predicate disambiguation | batch_69c68ab98c78819081743e614df04e1d |
completed | March 27, 2026, 1:48 p.m. |
Created at: March 27, 2026, 1:44 p.m.