Triple
T22346092
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Victor de Laveleye |
E552394
|
entity |
| Predicate | proposedSymbol |
P108502
|
FINISHED |
| Object | letter V as sign of victory |
—
|
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: letter V as sign of victory | Statement: [Victor de Laveleye, proposedSymbol, letter V as sign of victory]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: proposedSymbol Context triple: [Victor de Laveleye, proposedSymbol, letter V as sign of victory]
-
A.
proposedCurrencyName
Indicates that an entity has suggested or put forward a specific name to be used as a currency.
-
B.
nameProposedIn
Indicates that a particular name was suggested or put forward within a specific proposal, context, or event.
-
C.
definesSymbol
chosen
Indicates that one entity specifies or establishes another entity as a symbol representing some concept, value, or object.
-
D.
coProposedBy
Indicates that a proposal, idea, or item is jointly put forward or suggested by multiple entities together.
-
E.
symbolCreated
Indicates that one entity brought a symbol into existence, typically by designing, inventing, or originating it.
- 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_69e11e494eec81909c4d2d51f69499d9 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f157981c0881909ac74d68b99075c2 |
completed | April 29, 2026, 12:58 a.m. |
| PD | Predicate disambiguation | batch_69e7300c20088190a59e5bf9e70384f3 |
completed | April 21, 2026, 8:06 a.m. |
Created at: April 16, 2026, 8:43 p.m.