Triple
T5486233
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GJ-3 |
E123587
|
entity |
| Predicate | registrationPlatePrefix |
P29311
|
FINISHED |
| Object | GJ-3 |
—
|
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: GJ-3 | Statement: [GJ-3, registrationPlatePrefix, GJ-3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: registrationPlatePrefix Context triple: [GJ-3, registrationPlatePrefix, GJ-3]
-
A.
firstCharactersOfPlate
chosen
Indicates that one entity specifies the initial characters appearing at the beginning of another entity’s license plate identifier.
-
B.
isOnLicensePlateBeforeNumber
Indicates that one element appears on a license plate in a position preceding a specified number.
-
C.
registrationPrefix
Indicates that an entity has a specific registration prefix code assigned to it as part of its official registration or identification.
-
D.
civilRegistrationPrefixExample
Indicates that there is an example of a standard prefix used in civil registration identifiers or records.
-
E.
icaoRegionPrefix
Indicates the regional ICAO prefix that designates the geographic or administrative region associated with an aviation-related 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_69bd464a2d908190869324ce176779c8 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd93e5d0f08190a6cc9fc408b7c5bb |
completed | March 20, 2026, 6:37 p.m. |
| PD | Predicate disambiguation | batch_69bd91a73b148190a865243536a4fe76 |
completed | March 20, 2026, 6:27 p.m. |
Created at: March 20, 2026, 2:10 p.m.